Enforce pygrb_efficiency subsections #4909
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pygrb_efficiency
subsection in the config file for each injection set, i.e.[injections]
subsection.pygrb_efficiency
plots.Standard information about the request
This is a: bug fix. Prior to this fix,
pygrb_efficiency
was using a single value of lower/upper distance values, regardless of the injection set.This change affects: PyGRB
This change changes: result presentation plotting and scientific output
This change was tested by rerunning the results generation of a GRB analysis here. Note that the previous version of plots in this section was "jagged".